home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 1
/
Cream of the Crop 1.iso
/
PROGRAM
/
ALIB12.ARJ
/
SHR-WARE.DOC
< prev
next >
Wrap
Text File
|
1992-03-30
|
8KB
|
222 lines
SHR-WARE.DOC
Contents
Definition of Shareware . . . . . . . . . . . . . . . . . . . . . 1
Contacting ASP Members Via CompuServe . . . . . . . . . . . . . . 3
Author Address Changes . . . . . . . . . . . . . . . . . . . . . 3
ASP Ombudsman Policy . . . . . . . . . . . . . . . . . . . . . . 3
Definition of Shareware
Shareware distribution gives users a chance to try software before
buying it. If you try a Shareware program and continue using it, you
are expected to register. Individual programs differ on details --
some request registration while others require it, some specify a
maximum trial period. With registration, you get anything from the
simple right to continue using the software to an updated program with
printed manual.
Copyright laws apply to both Shareware and commercial software, and
the copyright holder retains all rights, with a few specific
exceptions as stated below. Shareware authors are accomplished
programmers, just like commercial authors, and the programs are of
comparable quality. (In both cases, there are good programs and bad
ones!) The main difference is in the method of distribution. The
author specifically grants the right to copy and distribute the
software, either to all and sundry or to a specific group. For
example, some authors require written permission before a commercial
disk vendor may copy their Shareware.
Shareware is a distribution method, not a type of software. You should
find software that suits your needs and pocketbook, whether it's
commercial or Shareware. The Shareware system makes fitting your needs
easier, because you can try before you buy. And because the overhead
is low, prices are low also. Shareware has the ultimate money-back
guarantee -- if you don't use the product, you don't pay for it.
Information on the Association of Shareware Professionals (ASP)
In the early days of shareware there were no real standards.
Independent authors had no efficient way to learn from each other or
to work together to improve the overall image of shareware. There was
no system in place to ensure that users were treated fairly and
professionally. There was no way for users to find an address for an
author who had moved. In short, the shareware community was
1
disorganized and each author did things the way he or she thought was
best. It was clear that if shareware was ever to become a viable and
respected marketing alternative, there had to be some standardization.
There had to be some guidelines to best serve the users.
In 1987 a handful of shareware authors founded the Association of
Shareware Professionals (ASP). In forming this industry association,
these shareware authors had several primary goals in mind, including:
o To inform users about shareware programs and about shareware
as a method of distributing and marketing software.
o To foster a high degree of professionalism among shareware
authors by setting programming, marketing, and support
standards for ASP members to follow.
o To encourage broader distribution of shareware through user
groups and disk dealers who agree to identify and explain
the nature of shareware.
o To assist members in marketing their software.
o To provide a forum through which ASP members may
communicate, share ideas, and learn from each other.
The newly formed Association of Shareware Professionals worked
together to draft a code of ethics for all present and future members.
This code of ethics included several requirements that soon became
very popular among users (customers), including:
o A member's program (evaluation version) could not be limited
(crippled) in any way. In the true spirit of
Try-Before-You-Buy, users must be able to evaluate all the
features in a program before paying the registration fee.
o Members must respond to every registration. At the very
least they must send a receipt for the payment.
o Members must provide technical support for their products
for at least 90 days from the date of registration.
A new system was put in place to help ensure that users were treated
fairly and professionally. If a user was unable to resolve a problem
with a member author then the user could contact the ASP Ombudsman
with their complaint. The Ombudsman would then try to help resolve
the dispute. For more complete details regarding the Ombudsman,
please refer to the "ASP Ombudsman Statement" below.
2
As of March, 1991, the ASP had over 300 author members and almost 200
vendor members, with new members joining every week.
Contacting ASP Members Via CompuServe
There is an easy and convenient way to speak directly to many ASP
Members (both authors and vendors). Visit the shareware forum on
CompuServe. Simply type "GO SHAREWARE", "GO SHARE", or "GO ASPFORUM"
from any CompuServe ! prompt.
Here you will be able to talk to the authors of your favorite
shareware programs, learn about other programs, ask questions, make
suggestions, and much more. We'd love to meet you online, please come
visit us today!
Author Address Changes
People move. Forwarding orders expire. What can you do?
"I got a copy of a shareware program written by an ASP Member. I sent
in the registration fee and the post office returned my letter saying
that it was undeliverable. Now what do I do?"
If the author has moved then chances are very good that you have an
old version of the program. This is another situation that the ASP
can help you to resolve. ASP Members are required to keep the ASP
informed of address changes. If you need to obtain the current
address for a member, simply write to the following address:
ASP Executive Director
545 Grover Road
Muskegon, MI 49442-9427
U.S.A.
or send a CompuServe message via CompuServe MAIL to ASP Executive
Director 72050,1433. You may also FAX your request to the ASP
Executive Director at 616-788-2765.
ASP Ombudsman Policy
This program is produced by a member of the Association of Shareware
Professionals (ASP). ASP wants to make sure that the shareware
principle works for you. If you are unable to resolve a shareware-
related problem with an ASP member by contacting the member directly,
ASP may be able to help. The ASP Ombudsman can help you resolve a
dispute or problem with an ASP member, but does not provide technical
3
support for members' products. Please write to the ASP Ombudsman at
545 Grover Road, Muskegon, MI 49442 or send a CompuServe message via
CompuServe Mail to ASP Ombudsman 70007,3536.
4